Source and delivery identities

• Fresh-main PR base: PSModule/Process-PSModule@64ffb1d87f86bd5d487891fdb140b78385a00531.
• Pushed candidate: PSModule/Process-PSModule@b8a2e4ff2056409f89289a3209f5b08c3ad42031, branch framework-contract-prose, base branch main.
• Complete scoped comparison: nine Markdown files, 47 insertions and 51 deletions. No other repository path changes.
• The draft opened after the first real slice, 9ba4a606ca4a6aa2e460b8e994c9fdc9eff82631. Small follow-ups are 769fad09b875efec70c2fc6199f9a9c53297990f, 30d6bc69fcf8ff9c0673e8c055a3b35927f69276, and b8a2e4ff2056409f89289a3209f5b08c3ad42031. No old proposal or first-pass PR is amended.
• Current source and issue-body ownership were rechecked before each commit. Main remained at the released source. The separate 🩹 [Patch]: Consumer artifacts stay under .PSModule #541 head remains 2001551566898e59efc764e68450c2238667d607 on complete-artifact-path-isolation; its proposal and owner branch are untouched. The recorded issue handback is the authority for existing pipeline prose, not permission to import that proposal's additions.

Writing sources

The fixed baseline is MSXOrg/docs@1b0d4893c8fefabe604d04393068a8ff6f848082/src/docs: Documentation Model, Natural Language, Writing Guide, Markdown, Documentation, and the applicable specification/design/reference/standard templates. Their artifact distinctions remain intact; no template scaffolding is added.

The official STE overview, FAQ, and relevant Issue 9 rules were read. Issue 9 rules 3.2, 3.6, 4.1-4.2, and 6.1-6.6 informed tense, active voice, short complete sentences, and descriptive paragraphs. The locally retained official PDF MD5 is 9c720341c350ed77943b2c73d01c716f, matching the official record. No manual content is republished. The bounded review and scans do not certify full ASD-STE100 conformance.

Complete reviewed scope and before/after evidence

All paths below are under docs/content/. The before text comes from the immutable PR base above; the after text is in the pushed candidate. Natural Language supplies en-US and direct language, the Documentation Model preserves normative contracts without implying implementation, and STE guidance supplies short complete sentences and active descriptive language.

The two no-change Git blob identities are exact on base and head: specification/spec.md is 5755abf2797a699e0ef0846ac2521cb1fb90b2bb; reference/scenario-matrix.md is d9c5490f5379fe94adf94df6ac349dfc0b82b8d1.

Preservation results

Pre-edit session evidence records concrete original text, its expected wording property, and source-backed acceptance before repository edits. Nine intended wording cases fail on the original source; all eleven page-level cases pass on the pushed candidate, including the two no-change cases. The session-only comparison reports zero preservation failures.

The protected passages include the public-API major policy, latest-version support policy, API-fingerprint section, both related automation-claim paragraphs, mocked-environment requirement, module-owned boundary-mock rule, linear maintenance policy, version resolution/publication sequence, pipeline runtime contract, root-only phase/discovery rules, framework-generated coverage guarantee, and stable publication/cleanup section. The fingerprint source is blob ee2eafdd83405ab42da7a25aa5f6e9ff367e6d5e, base lines 127-155; its section SHA-256 remains fb098e0eea00a129b7f87f13806acc104de6ad47439769355d2d2c8fcf824e23.

The selected main pipeline page contains neither a Consumer artifact root section nor a <WorkingDirectory>/.PSModule/ token. Both remain absent. Existing paths are unchanged; no unmatched proposal content or runner-only exception is added, removed, or reinterpreted.

Existing checks and accepted review

The existing repository Markdown configuration passes on all eleven explicit paths, before edits and on the completed source:

npx --no-install markdownlint-cli2 --config .github\linters\.markdown-lint.yml docs\content\specification\index.md docs\content\specification\spec.md docs\content\specification\design.md docs\content\specification\principles-and-practices.md docs\content\reference\pipeline-stages.md docs\content\reference\powershell-module-standard.md docs\content\reference\repository-standard.md docs\content\reference\scenario-matrix.md docs\content\reference\settings.md docs\content\reference\versioning.md docs\content\reference\workflow-inputs.md

Result: 11 files, 0 issues. An initial Windows wildcard invocation selected only seven files; it was corrected to the explicit eleven-file command above, not treated as full-scope evidence.

The existing site command, zensical build --clean from docs, passes before and after the changes with No issues found. git diff --check passes for the complete base-to-head change. The session-only preservation/wording command also passes at exact pushed head b8a2e4ff2056409f89289a3209f5b08c3ad42031.

No standalone documentation-link checker is present in this main tree. The link-check scripts named in the MSX Markdown standard belong to the MSX docs repository, not this repository. No dependency was installed; no enforcement tool, prose/inventory/implementation-shape snapshot test, or repository audit document is added.

All six applicable hosted checks succeed at the exact candidate: Docs Build and Lint, repository Lint code base, CodeQL, Actions analysis, and Copilot review. Publication is skipped as expected on the draft. Copilot review was explicitly requested with the CLI-supported @copilot value. Its completed review is APPROVED at b8a2e4ff2056409f89289a3209f5b08c3ad42031, with no inline comments or active issues. Docs run, repository lint run, and hosted review run retain the results.

The coordinating parent also accepted the content at this exact head after independently reading all nine changed-page diffs and comparing all eleven pages. Its comparison preserves headings, inline literals, destinations, fences, table rows, modality sequences, the fingerprint section and related automation text, and mocked-environment requirements. This records content acceptance only; the PR remains draft and no readiness or merge action is authorized.

Alignment and residual decisions

The delivery issue's pre-edit read, expectations, baseline, small-commit wording, ownership-recheck, and local current-head validation steps are complete. The scoped convergence sweep covered open documentation-writing-alignment issues, the protected follow-ups, the eleven owned paths, and the disjoint first-pass PR paths. No additional issue is closed by this bounded prose change.

Residual decisions are precise: #577 reconciles the unsupported fingerprint mechanism and related claims with the real resolver after #359/#524 producer decisions; #563 decides mock policy by test category; #573 decides bootstrap-core versus complete-public-API major policy. No runtime, framework upgrade, site redesign, release-label, readiness, merge, or automation change is made. This PR stays draft.

• Resolves [documentation-writing-alignment] State framework contracts without vague or unverified claims #562.
• References [documentation-writing-alignment] Reconcile API-fingerprint versioning claims with the resolver #577, with Default module release decisions to namespaced labels #359 and Module releases use configurable defaults and owned labels #524 as producer context.
• References [documentation-writing-alignment] Resolve conflicting mock requirements in module test guidance #563 and [documentation-writing-alignment] Resolve the bootstrap major-bump policy conflict #573 for the separate policy decisions.
• References 🩹 [Patch]: Consumer artifacts stay under .PSModule #541 for the separate pipeline-prose handback; its proposal and branch stay unchanged.